Type-Length-Value
Library with utilities for working with Type-Length-Value structures.
Example usage
This simple examples defines a zero-copy type with its discriminator.
use ;
// Give this type a non-derivable implementation of `Default` to write some data
// Account will have two sets of `get_base_len()` (8-byte discriminator and 4-byte length),
// and enough room for a `MyPodValue` and a `MyOtherPodValue`
let account_size = get_base_len + + \
get_base_len + ;
// Buffer likely comes from a Solana `solana_program::account_info::AccountInfo`,
// but this example just uses a vector.
let mut buffer = vec!;
// Unpack the base buffer as a TLV structure
let mut state = unpack.unwrap;
// Init and write default value
let value = state..unwrap;
// Update it in-place
value.data = 1;
// Init and write another default value
let other_value = state..unwrap;
assert_eq!;
// Update it in-place
other_value.data = 2;
// Later on, to work with it again
let value = state..unwrap;
// Or fetch it from an immutable buffer
let state = unpack.unwrap;
let value = state..unwrap;
Motivation
The Solana blockchain exposes slabs of bytes to on-chain programs, allowing program writers to intepret these bytes and change them however they wish. Currently, programs interpet account bytes as being only of one type. For example, an token mint account is only ever a token mint, an AMM pool account is only ever an AMM pool, a token metadata account can only hold token metadata, etc.
In a world of interfaces, a program will likely implement multiple interfaces. As a concrete and important example, imagine a token program where mints hold their own metadata. This means that a single account can be both a mint and metadata.
To allow easy implementation of multiple interfaces, accounts must be able to hold multiple different types within one opaque slab of bytes. The type-length-value scheme facilitates this exact case.
How it works
This library allows for holding multiple disparate types within the same account by encoding the type, then length, then value.
The type is an 8-byte ArrayDiscriminator
, which can be set to anything.
The length is a little-endian u32
.
The value is a slab of length
bytes that can be used however a program desires.
When searching through the buffer for a particular type, the library looks at
the first 8-byte discriminator. If it's all zeroes, this means it's uninitialized.
If not, it reads the next 4-byte length. If the discriminator matches, it returns
the next length
bytes. If not, it jumps ahead length
bytes and reads the
next 8-byte discriminator.
Serialization of variable-length types
The initial example works using the bytemuck
crate for zero-copy serialization
and deserialization. It's possible to use Borsh by implementing the VariableLenPack
trait on your type.
use ;
let initial_data = "This is a pretty cool test!";
// Allocate exactly the right size for the string, can go bigger if desired
let tlv_size = 4 + initial_data.len;
let account_size = get_base_len + tlv_size;
// Buffer likely comes from a Solana `solana_program::account_info::AccountInfo`,
// but this example just uses a vector.
let mut buffer = vec!;
let mut state = unpack.unwrap;
// No need to hold onto the bytes since we'll serialize back into the right place
let _ = state..unwrap;
let my_variable_len = MyVariableLenType ;
state.pack_variable_len_value.unwrap;
let deser = state..unwrap;
assert_eq!;